Redundant Instance Variable Initialization Elision

ABSTRACT

A compiler, IDE or other code analyzer may determine whether an instance variable declaration assignment is redundant. The code analyzer may also take action based on that determination. A code analyzer may be able to determine with certainty that a particular instance variable initialization or assignment is definitely redundant. The code analyzer may cause a compiler to automatically elide the redundant assignment from compiled source code. The code analyzer may be able to determine with certainty that a particular assignment is definitely not redundant. Additionally, a code analyzer may not be able to determine with certainty whether an instance variable assignment is definitely redundant or definitely not redundant. Additionally, the code analyzer may report a warning or other informative message indicating the redundancy property of the assignment, thus alerting the programming to a (possibly) redundant assignment.

BACKGROUND

Traditionally, IDE's may provide a source code analyzer, or may includethe ability to utilize an external (e.g., to plug in) an external sourcecode analyzer. Traditional source code analyzers may analyze theinitialization of instance variables within source code.

Instance variables explicitly initialized, in source code, to theirdefault values are, in many cases, redundant, as the Java LanguageSpecification guarantees that each instance variable is set to itsappropriate default initial value, when it is created. Explicitlyassigning an instance variable, in source code, with its default initialvalue is quite a common pattern, albeit unnecessary.

Existing source code analyzers may attempt to identify redundantassignments. However, in many cases the level of analysis provided bythese source code analyzers may be very basic. In certain situationstraditional source code analyzers may incorrectly identify assignmentsof default values as being redundant when they are not.

For example, a traditional source code analyzer may issue incorrectwarnings when the following simple example pseudocode is analyzed.

public class RedundInit { { x = 6; } int x = 0; // this assignment isnot redundant public static void main(String[ ] args) { RedundInit r =new RedundInit( ); System.out.println(r.x); } }

A traditional, existing, source code analyzer, such as Intellij IDEA™,may issue a redundant field initialization and recommend removing theinitialization of variable ‘x’ to ‘0’. However, if the initialization isremoved the program will then output an incorrect result (e.g., theprogram would print ‘6’, rather than ‘0’).

SUMMARY

Redundant Instance Variable Initialization Elision may involve extendingthe capabilities of a source code compiler, or other softwaredevelopment tools, to determine if an instance variable assignment is(possibly) redundant. A code analyzer may utilize an algorithm todetermine whether an instance variable assignment that is part of thevariable declaration is redundant, or possibly redundant. The codeanalyzer may then take some action based on that determination, such asindicating that the assignment is redundant or possibly redundant.

For instance, the code analyzer may cause the elision of the redundantinitialization or assignment. In other words, the code analyzer maycause a compiler to automatically elide the redundant initialization(e.g., assignment) completely from compiled source code, according tosome embodiments. In other embodiments, the code analyzer may report awarning or other informative message indicating that the assignment is(possibly) redundant—either in place of or in addition to causing theassignment to be elided.

In some embodiments, a code analyzer may be able to determine withcertainty that a particular instance variable initialization orassignment is definitely redundant. Similarly, the code analyzer may beable to determine with certainty that a particular instance variableinitialization or assignment is definitely not redundant. However, insome embodiments, a code analyzer may not be able to determine whetheran instance variable assignment is definitely redundant or definitelynot redundant. Thus, the code analyzer may determine that a particularinstance variable assignment is possibly redundant and indicate, such asby causing a compiler warning to be issued, that the assignment ispossibly redundant—thus, alerting the programmer to the possibility ofthe redundant assignment.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a logical block diagram illustrating a code analyzerconfigured to implement Redundant Instance Variable InitializationElision, according to one embodiment.

FIG. 2 is a flowchart illustrating one embodiment of a method forRedundant Instance Variable Initialization Elision, as described herein.

FIG. 3 is a flowchart illustrating one embodiment of a method fordetermining whether an instance variable assignment is redundant, asdescribed herein.

FIG. 4 is a flowchart illustrating one embodiment of a method fordetermining the redundancy property of an initial assignment for apossibly unassigned instance variable, as described herein.

FIG. 5 is a flowchart illustrating one embodiment of a method fordetermining whether an instance variable declaration assignment ispossibly redundant, as described herein.

FIG. 6 is a flowchart illustrating one embodiment of a method forRedundant Instance Variable Initialization Elision, as described herein.

FIG. 7 illustrates an example computing device suitable to implementRedundant Instance Variable Initialization Elision, according to someembodiments.

DETAILED DESCRIPTION OF EMBODIMENTS

Described herein are various methods, techniques and/or mechanisms forRedundant Instance Variable Initialization Elision. As noted above,Redundant Instance Variable Initialization Elision may involve extendingthe capabilities of a source code compiler, or other softwaredevelopment tools, to determine if an instance variable assignment is(possibly) redundant. According to some embodiments, a code analyzer mayutilize an algorithm to determine whether an instance variabledeclaration assignment (e.g., an assignment as part of a variabledeclaration) assigning a default initial constant value, is definitelyredundant, definitely not redundant, or possibly redundant.

The code analyzer may then take some action based on instance variabledeclaration assignment's redundancy property (e.g., whether it isdefinitely redundant, definitely not redundant, or possibly redundant).For instance, the code analyzer could cause the elision of the redundantinitialization or assignment. In other words, the code analyzer maycause a compiler to automatically elide the redundant initialization(e.g., assignment) completely from compiled source code, according tosome embodiments. In other embodiments, the code analyzer may report awarning or other informative message indicating that the assignment is(possibly) redundant—either in place of or in addition to causing theassignment to be elided.

In some embodiments, a code analyzer may be able to determine withcertainty that a particular instance variable initialization orassignment is definitely redundant. Similarly, the code analyzer may beable to determine with certainty that a particular instance variableinitialization or assignment is definitely not redundant. However, insome embodiments, a code analyzer may not be able to determine whetheran instance variable assignment is definitely redundant or definitelynot redundant. Thus, the code analyzer may determine that a particularinstance variable assignment is possibly redundant and indicate, such asby causing a compiler warning to be issued, that the assignment ispossibly redundant—thus, alerting the programmer to the possibility ofthe redundant assignment.

According to various embodiments, Redundant Instance VariableInitialization Elision may reduce the size of compiled source code, suchthat the compiled source code may require a smaller static footprint.Similarly, Redundant Instance Variable Initialization Elision may, insome embodiments, result in fewer actual byte code instructions to beexecuted, thus possibly increasing the performance of the compiledsource code. Additionally, Redundant Instance Variable InitializationElision may increase the readability of the source code by allowing thesource code to be written with explicit default initial assignmentinitializers, such that the expected default value of a variable may beobvious when the source code is visually inspected.

Thus, during compilation of source code, a compiler and/or code analyzermay analyze each instance variable to determine if it is ‘definitelyunassigned’, or ‘possibly unassigned’ at the point of its (i.e., theinstance variable's) declaration. An instance variable that is‘definitely unassigned’ at the point of its declaration, but that isexplicitly assigned (i.e., in the source code as part of thedeclaration), to the default initial constant value for its type (e.g.,as per the Java Language Specification, Chapter 4, section 12.5) can betreated by the compiler as if the assignment never happened (i.e. it canbe elided) without altering the behavior of the program. In other words,if the declaration for an instance variable assigns a value to thevariable that is equal to the variable type's default initial constantvalue, the assignment is unnecessary or redundant because the languagealready guarantees that the variable has that value when it is created(which may be earlier than when it is declared).

Similarly, an instance variable may be ‘possibly unassigned’ at thepoint of its declaration—that is an instance variable that has not beenassigned any value between its creation and the point in the source codewhere it is declared. According to some embodiments, a compiler and/orcode analyzer may issue a warning, hint, informational notice, etc.,that a ‘possibly unassigned’ instance variable explicitly assigned(i.e., in the source code at the point of declaration) the defaultinitial constant value for its type is most likely redundant.

As noted previously, Redundant Instance Variable Initialization Elisionmay, in some embodiments, provide several benefits. For instance,Redundant Instance Variable Initialization Elision may reduce the sizeof compiled source code, such that the compiled source code may requirea smaller static footprint. Similarly, Redundant Instance VariableInitialization Elision may, in some embodiments, result in fewer actualbyte code instructions to be executed, thus possibly increasing theperformance of the compiled source code.

Additionally, Redundant Instance Variable Initialization Elision mayincrease the readability of the source code by allowing the source codeto be written with explicit default initial assignment initializers,such that the expected default value of a variable may be obvious whenthe source code is visually inspected. For instance, programmers mayspecifically initialize instance variables. For example, a Booleanvariable may be initially set to FALSE and later set to TRUE, allowingthe life cycle of the variable to be clear (i.e., readable). In otherwords, allowing the initialization assignment to be present in thesource code, even when it is elided from the compiled code may allow aperson reading the source code to see the value to which a variable isinitialized without having to know/remember the default (initial) valuesfor each variable type within that programming language.

Thus, since, according to some embodiments, only the byte coderedundancy is removed (i.e., the assignment may still be present in thesource code) readability may be increased over not utilizing RedundantInstance Variable Initialization Elision described here and, instead,modifying the source code to directly remove the assignment.

In the following detailed description, numerous specific details are setforth to provide a thorough understanding of claimed subject matter.However, it will be understood by those skilled in the art that claimedsubject matter may be practiced without these specific details. In otherinstances, methods, apparatuses or systems are not described in detailbelow because they are known by one of ordinary skill in the art inorder not to obscure claimed subject matter.

While various embodiments are described herein by way of example forseveral embodiments and illustrative drawings, those skilled in the artwill recognize that embodiments are not limited to the embodiments ordrawings described. It should be understood that the drawings anddetailed description thereto are not intended to limit the embodimentsto the particular form disclosed, but on the contrary, the intention isto cover all modifications, equivalents and alternatives falling withinthe spirit and scope of the disclosure. Any headings used herein are fororganizational purposes only and are not meant to be used to limit thescope of the description. As used throughout this application, the word“may” is used in a permissive sense (i.e., meaning having the potentialto), rather than the mandatory sense (i.e., meaning must). Similarly,the words “include”, “including”, and “includes” mean including, but notlimited to. Additionally, when used in the claims, the term “or” is usedas an inclusive or and not as an exclusive or. For example, the phrase“at least one of x, y, or z” means any one of x, y, and z, as well asany combination thereof.

Some portions of the detailed description which follow are presented interms of algorithms or symbolic representations of operations on binarydigital signals stored within a memory of a specific apparatus orspecial purpose computing device or platform. In the context of thisparticular specification, the term specific apparatus or the likeincludes a general purpose computer once it is programmed to performparticular functions pursuant to instructions from program software.Algorithmic descriptions or symbolic representations are examples oftechniques used by those of ordinary skill in the signal processing orrelated arts to convey the substance of their work to others skilled inthe art. An algorithm is here, and is generally, considered to be aself-consistent sequence of operations or similar signal processingleading to a desired result. In this context, operations or processinginvolve physical manipulation of physical quantities. Typically,although not necessarily, such quantities may take the form ofelectrical or magnetic signals capable of being stored, transferred,combined, compared or otherwise manipulated. It has proven convenient attimes, principally for reasons of common usage, to refer to such signalsas bits, data, values, elements, symbols, characters, terms, numbers,numerals or the like. It should be understood, however, that all ofthese or similar terms are to be associated with appropriate physicalquantities and are merely convenient labels. Unless specifically statedotherwise, as apparent from the following discussion, it is appreciatedthat throughout this specification discussions utilizing terms such as“processing,” “computing,” “calculating,” “determining” or the likerefer to actions or processes of a specific apparatus, such as a specialpurpose computer or a similar special purpose electronic computingdevice. In the context of this specification, therefore, a specialpurpose computer or a similar special purpose electronic computingdevice is capable of manipulating or transforming signals, typicallyrepresented as physical electronic or magnetic quantities withinmemories, registers, or other information storage devices, transmissiondevices, or display devices of the special purpose computer or similarspecial purpose electronic computing device.

Turning now to FIG. 1, which shows a flowchart illustrating oneembodiment of a method for Redundant Instance Variable InitializationElision, as described herein. FIG. 1 illustrates, according to oneembodiment, a workflow for compiling and executing a computer program.For purposes of illustration, the following description is providedlargely in the context of using the Java′ programming language. However,it is noted that the techniques described may be used with any ofvarious programming languages that support instance variable declarationassignments and that provides default initial constant values forvariables at creation and according to the variable type.

For example, various programming languages, such as Java™ and C# maygive variables a default initial constant value at creation. Forinstance, according to the Java programming language, variables aregiven a type-specific default initial constant value when they arecreated. The listing below shows example type-specific default initialconstant values according to a Java-based example:

For type ‘byte’, the default value is zero, that is, the value of(byte)0.

For type ‘short’, the default value is zero, that is, the value of(short)0.

For type ‘int’, the default value is zero, that is, 0.

For type ‘long’, the default value is zero, that is, 0L.

For type ‘float’, the default value is positive zero, that is, 0.0f.

For type ‘double’, the default value is positive zero, that is, 0.0d.

For type ‘char’, the default value is the null character, that is,‘\u0000’.

For type ‘boolean’, the default value is ‘false’.

For all reference types (§4.3), the default value is ‘null’.

In various embodiments, source code 120 may be specified in variousprogramming languages, such as Java™, C#, and/or other programminglanguages. For example, source code may be provided as a set of .javafiles in embodiments where Java′ is being used. In some embodiments,source code 120 may be specified using a combination of languages, whichmay include one or more low-level and/or intermediate languages (e.g.,assembly). In general, a class may be considered a user-defined type ordata structure that may include data, variables, functions, methodsand/or other attributes as members and that represents a definition,blueprint, or template, for creating programming objects of a specifictype. A class may provide initial values for data members andimplementations for member functions and methods. Classes are frequentlyincluded in libraries. A library may be considered a collection ofresources used by software programs or applications. A library mayinclude any of various types of resources including, but not limited to,data, documentation, classes, subroutines, and/or type specifications,according to some embodiments. A library may be organized so as to beutilized by more than one application (possibly at the same time), andmay promote re-usability by providing resources so that applications maynot have to implement (or re-implement) the same behavior.

The compiler 160 may analyze the source code 120 to produce anexecutable version of the program or bytecode files, such as compiledcode 180 (e.g., .class files or jar files in the case of Java™) in thedepicted embodiment. In some embodiments, compiler 160 may utilize codeanalyzer 140 to analyze source code 120—in part or in whole. In someembodiments, code analyzer 140 may be separate and distinct fromcompiler 160, while in other embodiments, code analyzer 140 may beconsidered a part of compiler 160. In some embodiments, code analyzer140 and/or compiler 160 may be part of an integrated developmentenvironment, such as integrated development environment 100, configuredto provide various complete software development tools.

Different types of executable code formats may be used in variousembodiments. For example, binary machine language may be used instead ofbytecodes. In some scenarios, parts of the executable code (e.g.,compiled code 180) may be in bytecode while others are in a nativebinary machine language.

As part of compiling source code 120 into executable code (e.g.,complied code 180), the compiler 160, and/or code analyzer 140, mayperform a sequence of analysis operations on source code 120, such as toapply or implement Redundant Instance Variable Initialization Elision,according to some embodiments. For example, the code analyzer 140 and/orthe compiler 160 may apply analysis rules 150 to determine that theinitial assignments of one or more instance variables (at the point oftheir declaration) in source code 120 are redundant. Analysis rules 150may be any form of rules, heuristics, analysis methods, etc. usable todetermine whether instance variable initializations and/or assignmentsare definitely redundant, definitely not redundant, or possiblyredundant, according to various embodiments. Analysis rules 150 may varyfrom programming language to programming language and may be specificfor a particular programming language, according to various embodiments.

Thus, Redundant Instance Variable Initialization Elision, as describedherein, may, according to various embodiments, identify three differentcategories of instance variable initialization assignment: 1) definitelyredundant and it can be safely omitted from a compiled version of thecode, 2) definitely not redundant because the code analyzer encounters amodification to the instance variable and no warnings may be generated,3) possibly redundant where it is not possible to determine staticallythat there is no modification to the instance variable, but in whichthere may not actually be a modification to the instance variable atruntime.

While illustrated as being a part of code analyzer 140, in someembodiments, analysis rules 150 (as well as possibly code analyzer 140)may be part of compiler 160 and/or integrated development environment100. In one embodiment, analysis rules 150 may represent logic coded aspart of code analyzer 140, while in other embodiments, analysis rules150 may represent a data structure encoding logic accessible and usableby code analyzer 140.

In response to determining that a particular assignment is definitelyredundant, code analyzer 140 may perform one or more actions, such asissuing a developer warning through integrated development environment100, communicating a compiler hint to compiler 160, and/or causingcompiler 160 to automatically omit the redundant assignments from thecompiled code 180 (e.g., without requiring any developer action),according to various embodiments.

As shown in FIG. 1, a code analyzer 140 may access source code 120 inorder to, among other things, identify redundant instance variableinitializations, according to some embodiments. If an instance variableinitialization is determined to be redundant (e.g., definitelyredundant), code analyzer may indicate the initialization's redundancyin any of various ways, according to different embodiments.Additionally, code analyzer 140 may inform compiler 160 (e.g., via anyof various ways) and compiler 160 may omit the redundant assignment whengenerating compiled code 180 from source code 120. For instance,compiler 160, may omit the assignment in response to the indication thatthe initialization was redundant, according to one embodiment.

Code analyzer 140 may represent any of various types of code analyzers,such as a stand-alone code analyzer, an IDE-based code analyzer, acompiler-based code analyzer, etc., according to various embodiments.Thus, in some embodiments, code analyzer 140 may be separate fromcompiler 160, but in other embodiments, code analyzer 140 may be part ofcompiler 160. In yet other embodiments, code analyzer 140 and compiler160 may be part of an IDE, such as integrated development environment100, as shown in FIG. 1.

As noted above, many traditional IDE's and/or other code analysis toolsimplement a very simply technique for detecting redundant assignments.Whenever it is found that a field is being initialized to its defaultvalue, a traditional IDE and/or code analysis tool may generate awarning. However, as will be described in more detail below, there is anentire class of problems where the initialization may actually beneeded, even if the variable is being initialized to its default initialconstant value. For example, in some embodiments, the field (e.g.,variable) may have changed between the time it was created (and givenits default initial constant value) and the time is declared andinitially assigned.

Traditionally, code analysis tools may only provide warnings regardingredundant initializations without actually determining whether aparticular instance variable initialization is definitely redundant.Additionally, existing code analysis tools do not elide (e.g.,automatically) a redundant assignment from complied code. Furthermore,traditional IDEs and/or code analysis tools also frequently generateincorrect warnings that particular assignments are redundant insituations where the initialization is actually required for properfunctioning of the compiled code. Thus, in some cases existing codeanalysis tools may provide incorrect warnings that lead a developer tothink that a particular variable initialization may be removed from thesource code, however, removing the initialization may cause problems inthe execution of the compiled code because the initialization was notactually redundant.

According to some embodiments, Redundant Instance VariableInitialization Elision may be used with, or as part of, various tools,such as code analyzer 140, compiler 160, integrated developmentenvironment 100, and/or virtually any other tool that provides codeanalysis. In some embodiments, a tool configured to implement RedundantInstance Variable Initialization Elision may modify the code (e.g., thesource code 120 and/or the compiled code 180). In other embodimentshowever, a tool configured to implement Redundant Instance VariableInitialization Elision may not modify any code, but instead may beconfigured to provide more accurate information (e.g., to a user ordeveloper) regarding initialization and assignments in the code. Forinstance, the code analyzer 140 may provide a user information regardingthe redundancy property (e.g., whether redundant or not) of variousinstance variable initializations assignments in source code 120.

As described above, many programming languages, such as the Java™programming language uses various default assignments to variables. Forinstance, the Java programming language utilizes various default valuesfor variables according to the type of the variable. For instance, aprogramming language may use one default value for one variable type,while using a different default value for a different variable type.Some programming languages guarantee that a variable, such as aninstance variable, is assigned a default value prior to any use of thatvariable during code execution.

Thus, if the declaration of a particular instance variable includes anassignment of the variable's default value to the variable, the actualassignment at the point of the declaration may be redundant, since theprogramming language may already guarantee that the variable has thedefault value.

For example, the following example Java pseudocode illustrates aredundant instance variable assignment (or initialization).

Example 1 class Foo { int bar = 0; }

In the example above, the assignment of ‘0’ to the instance variable‘bar’ is redundant, since, the Java programming language, according tothe Java Language Specification (JLS) guarantees that the value of ‘bar’will be ‘0’, when it is created. Thus, in some embodiments, if sourcecode including the code of the above example were analyzed by codeanalyzer 140 (e.g., a code analyzer configured to implement RedundantInstance Variable Initialization Elision), code analyzer 140 maydetermine that the assignment of ‘0’ to the instance variable ‘bar’ isredundant and may, in response, indicate the redundant property of theassignment. For instance, in one embodiment, the code analyzer 140 maycommunicate with compiler 160, such as via a compiler hint, to indicatethat the assignment of ‘0’ to the instance variable ‘bar’ at the pointof declaration is redundant and may be omitted from a compiled versionof the source code 150. In response to the indication that the instancevariable assignment is redundant the compiler 160 may omit theassignment from compiled code 180, according to one embodiment.

Similarly, the following example Java pseudocode illustrates multipleinstance variable initial assignments that are all redundant, accordingto one example embodiment.

Example 2 class Baz { byte b = (byte)0; // aload_0 iconst_0 putfieldidx1 idx2 short s = (short)0; // aload_0 iconst_0 putfield idx1 idx2 inti = 0; // aload_0 iconst_0 putfield idx1 idx2 long l1 = 0L;  // aload_0lconst_0 putfield idx1 idx2 float f = 0.0f;  // aload_0fconst_0 putfield idx1 idx2 double d = 0.0d;  // aload_0dconst_0 putfield idx1  idx2 char c = ‘\u0000’; // aload_0iconst_0 putfield idx1 idx2 boolean bo = false;  // aload_0iconst_0 putfield idx1  idx2 Object obj = null;  // aload_0aconst_null putfield idx1  idx2 }

In the above example, the assignments of all the instance variables in‘Baz’ are redundant. Additionally, in a Java based embodiments, theassignments may typically translate to five bytes of code, perassignment, per instance constructor, in the compiled source code. Thecomments in the above example, illustrate typical byte codes of compiledsource code for the assignments, according to a Java-based embodiment.

The two examples above are similar to each other, each showing anexample of an assignment to a default initial constant value that isredundant and which may be removed from the compiled version of thesource code without affecting the behavior of the compiled code,according to some embodiments. Both of the above examples illustratessituations in which code analyzer 140 may positively determine that theinstance variable declaration assignment is definitely redundant and maybe safely (i.e., in terms of execution behavior) removed from thecompiled code. As will be discussed in more detail below, according tosome embodiments, a compiler 160 may automatically omit a definitelyredundant assignment a compiled version of the source code 120, such asfrom compiled code 180, without requiring the developer to actuallyremove the assignment from the source code (as is frequently required bytraditional code analysis tools).

The following example Java pseudocode illustrates an additional instancevariable initial assignment that is redundant, according to one exampleembodiment.

Example 3 class Foo { { noOp( ); } int bar = 0; private final void noOp() { } }

In the above Java-based example, the assignment of ‘0’ to the instancevariable ‘bar’ is ‘probably redundant’, (since the Java ProgrammingLanguage, according to the JLS, may guarantee that the value of ‘bar’will be ‘0’ when it is created). In fact, in the above exampleembodiment, the assignment to ‘bar’ is redundant, as the method ‘noOp’does not assign any value to it. Thus, in one embodiment, code analyzer140 may, when analyzer source code illustrated by the above example,determine that the initial assignment of ‘0’ to instance variable ‘bar’is redundant.

Not every initial assignment of an instance variable may be redundant,however. For example, if an instance variable is initially assigned (atthe point of declaration) a value other than its initial defaultconstant value, a code analyzer, such as code analyzer 140, maydetermine that the initial assignment of the variable is not redundant,according to some embodiments.

Additionally, many programming languages may allow various types ofprogramming instructions, structures, constructions, models, executionpaths, etc., permitting an instance variable to be modified prior to theactual declaration of that variable in the code. For instance, aninstance initializer and/or instance variable initializer may change thevalue of an instance variable before the point (e.g., in terms ofexecution) of the variable actual declaration and initial assignment.Thus, if the instance variable is initially assigned (i.e., at the pointof declaration) to the default initial constant value for the relevanttype, that assignment may not be redundant because the instance(variable) initializer may have previously modified (e.g., assigned avalue to) the variable (and thus, the initial assignment is ‘resetting’the variable to its default initial constant value, according to oneexample embodiment.

For instance, in a Java-based embodiment, whenever a field contains anassignment, such as variable ‘bar’ in the above example, the assignmentmay be copied to by the compiler into the constructor(s) of the class,such as within the constructor of class ‘Foo’ above. Thus, theconstructor of class ‘Foo’ would contain a call to noOp( ) and then anassignment to ‘bar’. Every time an instance of ‘Foo’ is created, therewould be a method call and an assignment of ‘0’ to variable ‘bar’.However, when the method is called, the logic inside the method may alsoperform assignments to the variable ‘bar’. For instance, the body of themethod noOp( ) could include the assignment “bar=5” making theinitialization of ‘bar’ as part of its declaration (e.g. “int bar=0;” nolonger redundant. Instead, the initialization would be resetting thevalue of variable ‘bar’ back to ‘0’, according to one exampleembodiment.

For instance, the following example Java pseudocode illustrates aninstance variable initial assignment that is not redundant, according toone example embodiment.

Example 4 class Foo { { setBar( ); } int bar = 0; private final voidsetBar( ) { bar = 5; } }

In the above example, the assignment of ‘0’ to the instance variable‘bar’ is NOT redundant. It is necessary, for correctness, that ‘bar’ isset to ‘0’ at the point in the source code where it is declared,according to the above example embodiment. Thus, code analyzer 140, whenanalyzing code according to the above example, may determine that theinitial assignment of ‘0’ to variable ‘bar’ at the point of declarationis not redundant, according to some embodiments.

In cases where a method call is made within a constructor, as in theabove example, the code analyzer 140 may not be able to determine theexact instructions to be executed within the body of method call,depending on the nature of the method, according to some embodiments.For instance in the Java-based example above, the method setBar( ) isboth private and final. Since the method setBar( ) is private and nooverriding can take place (e.g., there is only one method body that canbe called), code analyzer 140 may determine the result of the method.Thus, code analyzer 140 may look inside the body of the method todetermine if any instruction affects the variable ‘bar’. Since, the bodyof method setBar( ) includes the instruction, “bar=5”, code analyzer 140may determine that the initialization of ‘bar’ during its declaration isdefinitely not redundant, according to one example embodiment.Conversely, referring back to Example 3 above, since the body of methodnoOp( ) is empty, code analyzer 140 may determine that theinitialization of variable ‘bar’ (in Example 3) is definitely redundant,according to one example embodiment.

However, in some cases a method called as part of an instanceinitializer (or an instance variable initializer) may be overridable(e.g., it may not be final or private). In some embodiments, there maybe one or more overridable methods called as part of an initializer.When such a method may be overridden, one version may modify the valueof an instance variable and another may not. In some embodiments, codeanalyzer 140 may not be able to determine exactly which method body maybe executed at runtime, and may not be able to determine whether or nota particular instance variable assignment will be redundant duringexecution because it may be impossible to determine which method bodywill be executed.

Additionally, in some cases, an instance variable may be modified via areference. In such a case there may not be a method call. For instance,an instance variable may be modified via a reference pointer to theobject containing the instance variable. The following example Javapseudocode illustrates another example of a non-redundant instancevariable initialization assigning the variable's default initialconstant value when it is declared.

Example 5 class Foo { { Foo fooRef = this; fooRef.bar = new Object( ); }Object bar = null; }

In the example above, the assignment of ‘null’ to the instance variable‘bar’ is NOT redundant. As shown above, a variable, ‘fooRef’, getsassigned ‘this’ which is the instance being created. In some programminglanguages this may be referred to as ‘aliasing’. The ‘forRef’ variablemay be used to modify the value of variable ‘bar’, as shown in the aboveexample. Thus, the variable ‘bar’ may be modified through anintermediate variable that points to the same instance that is beingcreated. Subsequently, the variable ‘bar’ may be assigned the value of‘null’ (e.g., the default initial constant value for its type).

In this example case, the assignment (e.g., of ‘null’ to ‘bar’) is notredundant because ‘bar’ is changed in the code prior to its initialassignment at the point when it is declared. If the assignment of ‘null’to ‘bar’ were to be removed, the example code would not functioncorrectly. For correctness ‘bar’ is set to ‘null’ at the point in thesource code where it is declared, according to the example embodiment.

However, in some embodiments code analyzer 140 may not be able todetermine for certain whether an instance variable initial assignment isdefinitely redundant, such as with the aliasing example illustrated inthe above example. Thus, according to some embodiments, code analyzer140 may be configured to indicate that a particular instance variableinitialization is possibly redundant and that it cannot be determinedwith certainty whether the initial assignment is definitely redundant ornot. In other words, there may be some situations where a code analyzer140 may not be able to tell from code analysis whether an assignment isnecessarily redundant or not, in which case the code analyzer 140 mayidentify the assignment as possibly redundant and/or issue some sort ofwarning, note, compiler hint, etc.

Redundant Instance Variable Initialization Elision, as described herein,may involve more than one type of code analysis. For ease of discussionthe analysis utilized by Redundant Instance Variable InitializationElision may be considered to divide the problem space into two stages.For instance, the first stage of analysis may identify simple cases inwhich code analyzer 140 may be able to determine for certain whether anassignment is definitely redundant or definitely not redundant. Thesecond stage of analysis may be utilized in cases when it cannot easilybe determined whether an assignment is redundant or not. For instance,Examples 1 and 2 above may fall into the first situation and theredundancy property of the assignments may be determined by the first(logic) stage of analysis, but Examples 3 and 4 may fall into the secondsituation and the redundancy property of the assignments may bedetermined by the second (logic) stage of analysis. Note that the codeanalysis described herein in only divided into separate stages for easeof discussion and no real separation may occur when implementingRedundant Instance Variable Initialization Elision, according to variousembodiments.

In many situations, the analysis may be utilized to determine withcertainty whether an assignment (e.g., an instance variable initialassignment as the point of declaration) is redundant. Additionally, aset of rules (e.g., heuristics), such as analysis rules 150, may beutilized to identify an assignment as potentially being redundant (e.g.,possibly redundant). Thus, tools implementing Redundant InstanceVariable Initialization Elision, such as code analyzer 140, may be ableto clearly indicate to a developer the specific category (e.g.,definitely redundant, definitely not redundant, or possibly redundant)into which a particular assignment falls.

FIG. 2 is a flowchart illustrating one embodiment of a method forRedundant Instance Variable Initialization Elision, as described herein.As shown in block 200, a code analyzer, such as code analyzer 140, mayaccess source code, such as source code 120 and may identify an instancevariable declaration that includes an assignment assigning a value tothe instance variable, as shown in block 210.

If the value assigned to the instance variable at the point ofdeclaration (i.e., the assigned value) is the default initial constantvalue for the variable type, as shown by the positive output of decisionblock 220, code analyzer 140 may apply analysis rules 150, to determinewhether the instance variable declaration assignment is definitelyredundant with respect to the default initial constant value, as shownin block 230. When applying analysis rules 150, code analyzer 140 mayapply any of various methods of analysis, such as the two logical stagesof code analysis described above. For instance, code analyzer 140 mayfirst determine whether the instance variable declaration under analysisfalls under one of the simple categories, such as those describedregarding Examples 1 and 2, above, according to one embodiment.

If the code analyzer 140 determines that the assignment is definitelyredundant, as illustrated by the positive output of decision block 240,the code analyzer 140 may indicate that the assignment is definitelyredundant, as shown in block 250, according to some embodiments. Forexample, in one embodiment, in response to determining that anassignment is definitely redundant, code analyzer 140 may issue awarning, such as a user/developer warning, compiler hint, etc.,indicating that the assignment is definitely redundant and may alsorecommend that the assignment can be omitted.

In other embodiments, code analyzer 140 may communicate directly tocompiler 160 to enable compiler 160 to omit the definitely redundantassignment from compiler code 180. For example, compiler 160 may, aspart of compiling source code 120, initiate analysis of source code 120by code analyzer 140. In turn, code analyzer 140 may return informationindicating one or more definitely redundant assignments, and compiler160 may then omit those definitely redundant assignments from compiledcode 180.

However, if the assigned value (e.g., the value assigned to thevariable) is not the variable's default initial constant value, asindicated by the negative output of decision block 220, code analyzer140 may not need to apply analysis rules 150, because the fact that itis being assigned a value other that the default initial constant valuemay be enough for code analyzer 140 to determine that the assignment isdefinitely not redundant.

If, as indicated by the negative output of decision block 240, theassignment is not definitely redundant, code analyzer 140 may then applyadditional analysis to determine whether the assignment is redundant ornot, as will be described below regarding FIGS. 3-5, below.

FIG. 3 is flowchart illustrating one embodiment of a method fordetermining whether an instance variable assignment is redundant, asdescribed herein. As described above, a code analyzer configured toimplement Redundant Instance Variable Initialization Elision, such asanalyzer 140, may apply analysis rules 150 to determine whether aninstance variable declaration assignment is definitely redundant withrespect to a default initial constant value for the variable's type, asshown in block 300.

If, as indicated by the positive output of decision block 310, the codeanalyzer 140 determines that the instance variable is definitelyassigned prior to the instance variable declaration, the code analyzer140 may determine that the instance variable declaration assignment isdefinitely not redundant, as shown in block 320.

In some embodiments, code analyzer 140 may apply a set of rules, such asmay be part of analysis rules 150, to determine whether an instancevariable is definitely assigned prior to the variable's declaration. Forinstance, in one Java-based embodiment, code analyzer 140 may beconfigured to follow the logic described in the Java LanguageSpecification (e.g., chapter 16) to determine whether the instancevariable is definitely assigned prior to the variable's declaration. Forexample, code analyzer 140 may examine each method body that may becalled from the class instance (variable) initializer to determinewhether any instruction modifies the instance variable. If a method body(for a method executed prior to the variable's declaration) includes aninstruction that modifies the variable (or causes the variable to bemodified) code analyzer 140 may determine that the instance variable isdefinitely assigned prior to its declaration.

If, however, the code analyzer 140 determines that the instance variableis not definitely assigned prior to the instance variable declaration,as indicated by the negative output of decision block 310, the codeanalyzer 140 may determine that the instance variable declarationassignment is possibly redundant, as shown in block 330, and may performadditional analysis in order to determine whether the instance variabledeclaration assignment is redundant or not, as will be described belowregarding FIGS. 4 and 5.

When determining whether an instance variable is assigned prior to itsdeclaration, a code analyzer may analyze, among other things, theinstance variables in the source code being compiled. By analyzing eachnon-final, non-volatile, instance variable that is initialized with itsdefault initial constant value, a code analyzer may determine if thevariable is definitely unassigned (or not) at the point of thedeclaration of the instance variable. Thus, determining whether avariable is definitely redundant may involve determining that there hasbeen no previous assignment of this variable at this particulardeclaration point.

A code analyzer may be configured to use any of various methods ofanalysis and/or logic rules (that may be specific to the particularprogramming language in which the source code was written) to determinewhether an instance variable is unassigned prior to its declaration. Forexample, a code analyzer may examine the code that appears (andexecutes) before the instance variable declaration to determine whetherthe variable is assigned a value. In one embodiment, a code analyzer,such as code analyzer 140, may examine the code that executes prior tothe instance variable declaration to determine whether the variable(e.g., the variable name) appears on the left-hand side of anyassignments. If the variable does not appear on the left-hand side ofany assignment, code analyzer 140 may determine that the variable is notassigned a value prior to its declaration and is therefore definitelyunassigned (i.e., at the point of the variable's declaration). Asanother example, code analyzer 140 may use the logic described in theJava Language Specification (e.g., chapter 16) to determine whether theinstance variable is definitely unassigned prior to the variable'sdeclaration, in one Java-based embodiment.

Note that as described herein, whether a variable is unassigned prior toits declaration does not refer to it being given its default initialconstant value at creation. Thus, code analyzer 140 may determinewhether an instance variable is unassigned between the point at which itis created (and given its default initial constant value) and the pointat which it is declared, according to an execution order of the sourcecode 120 when executed as compiled code 180.

While code analyzer 140 may utilize language specific rules fordetermining whether a field is definitely unassigned, as the exactprogramming structures, constructs, methods, methodologies, etc., thatallow a field (e.g., an instance variable) to be modified may vary fromlanguage to language and from embodiment to embodiment. Additionally,while analysis rules 150 may include one or more analysis method thatdefine how to determine if a variable is definitely unassigned, theremay be other ways in which a variable may be modified that are notcovered by the rules configured to determine whether a variable isdefinitely assigned or definitely unassigned.

If an instance variable is ‘definitely unassigned’ and there is nopotential of its modification (as above), before its declaration, thencode analyzer 140 may determine that the instance variable declarationassignment is ‘definitely redundant’ and compiler 160 may elide the bytecodes that perform the assignment from the generated output, withoutchanging the behavior of the program.

Thus, code analyzer 140 may be configured to apply one set of analysismethods or rules to see if a particular instance variable falls into adefinitely assigned category or into a definitely unassigned category,but may also determine that an instance variable falls in between thesecategories. In other words, just because one analysis method may not beable to determine that an instance variable is definitely unassigned,there may be situations in which the variable may be modified that arenot covered by those rules.

FIG. 4 is a flowchart illustrating one embodiment of a method fordetermining the redundancy property of an initial assignment for apossibly unassigned instance variable, as described herein.

As shown in block 400, a code analyzer configured to implement RedundantInstance Variable Initialization Elision, such as code analyzer 140, maydetermine that an instance variable is possibly unassigned prior to theinstance variable's declaration assignment and may further determinewhether the source code includes any code blocks that could possiblyassign a value to the instance variable prior to the instance variabledeclaration, as shown in decision block 410.

Note that a code analyzer may determine whether a code block couldpossibly assign value by examining/analyzing how the code block iscurrently written in the source code. The term ‘could possibly assign’does not refer to the fact that the source code may be modified toinclude an assignment, but rather that the code block—as currentlywritten in the source code—could possibly assign a value to the instancevariable prior to, according to the execution order of the source codewhen executed, the declaration of the instance variable (e.g., thedeclaration that includes the initialization or initial assignment).

If, as indicated by the negative output of decision block 410, the codeanalyzer 140 determines that the source code does not include any codeblocks that could possibly assign a value to the instance variable priorto the instance variable declaration, the code analyzer 140 maydetermine that the assignment is definitely redundant, as shown in block460. As noted previously, when the code analyzer 140 determines that aninstance variable declaration assignment is definitely redundant, it maytake any of various types of actions, such as indicating (e.g., byproviding a warning, compiler hint, source code comment, etc.) that theassignment is definitely redundant.

If, as indicated by the positive output of decision block 410, the codeanalyzer 140 determines that the source code includes at least one(e.g., one or more) code blocks that could possibly assign a value tothe instance variable prior to the instance variable declaration, thecode analyzer 140 may apply a set of rules, such as analysis rules 150,to determine whether any of the code blocks definitely assigns a valueto the instance variable prior to the instance variable declaration, asin block 420.

As noted above, code analyzer 140 may apply a set of rules, such as maybe part of analysis rules 150, to determine whether an instance variableis definitely assigned prior to the variable's declaration. Codeanalyzer 140 may examine each method body that may be called from theclass constructor to determine whether any instruction modifies theinstance variable, according to one embodiment. If a method body (for amethod executed prior to the variable's declaration) includes aninstruction that modifies the variable (or causes the variable to bemodified) code analyzer 140 may determine that the instance variable isdefinitely assigned prior to its declaration.

If, as indicated by the positive output of decision block 430, the codeanalyzer 140 determines that at least one code block definitely assignsa value to the instance variable prior to the instance variabledeclaration, the code analyzer 140 may determine that the instancevariable declaration assignment is definitely not redundant, as in block440.

If, as indicated by the negative output of decision block 430, the codeanalyzer 140 determines that none of the code blocks definitely assignsa value to the instance variable prior to the instance variabledeclaration assignment, the code analyzer 140 may determine that theinstance variable declaration assignment is possibly redundant, as inblock 450.

FIG. 5 is a flowchart illustrating one embodiment of a method fordetermining whether an instance variable declaration assignment ispossibly redundant, as described herein.

As described above, a code analyzer configured to implement RedundantInstance Variable Initialization Elision, such as code analyzer 140, maydetermine that an instance variable declaration assignment is possiblyredundant, as in block 500. For instance, in some embodiments, the codeanalyzer 140 may not be able to determine, based on the analysisdescribed above regarding FIGS. 3 and 4, whether an instance variabledeclaration assignment is definitely redundant or definitely notredundant and may thus apply additional analysis to the source code withregard to that particular instance variable declaration assignment inorder to attempt to determine a redundancy property (e.g., definitelyredundant, definitely not redundant, or possibly redundant) for thatparticular instance variable declaration assignment.

As illustrated in decision block 510, the code analyzer 140 may beconfigured to determine whether any earlier code block (e.g., any codeblock that occurs prior to the instance variable declaration, accordingto the execution order of the source code) includes certain types ofprogramming instructions, structures, constructions, models, executionpaths, etc., that may permit the value of the instance variable to bemodified prior to its declaration.

An instance variable may be assigned in a way that is not detectable bythe methodology described above regarding determine whether an instancevariable is definitely assigned or definitely unassigned prior to itsdeclaration. There are a number of ways in which this can occur,according to various embodiments. For example, according to a Java-basedexample, if there is one of the following, in left-to-right order inwhich they appear textually in the source code, before the instancevariable declaration, an instance variable may have been modified priorto its declaration:

1. a method invocation; or

2. an inner class construction; or

3. a lambda capturing the ‘this’ object; or

4. a new class construction being passed ‘this’; or

5. an assignment where the right side evaluates to ‘this’.

For example, when an inner class in created, a java-based compiler mayimplicitly pass the inclosing instance to the inner class. Variables inthe outer scope may be modified from inside the inner class. The samesituation may exist for Lambdas, or for a created class that is passed‘this’ as a parameter to the newly created class. Similarly, an instancevariable may be modified using an assignment in which right hand sideuses ‘this’. In general, according to Java-based embodiments, if thereis a chance that some block of code will have access to ‘this’, there isa potential for that code to modify the variable.

Thus, according to a Java-based embodiment, the code analyzer 140 may beconfigured to determine whether any earlier code block includes a methodinvocation, an inner class construction, a lambda expression capturing‘this’, a new class construction that is passed ‘this’, or an assignmentwith ‘this’ on the right side. While described herein in terms of‘this’, in some embodiments according to some programming languages, anyblock of code that uses an object pointer to the object that includesthe instance variable may be used to modify the instance variable andthus may be identified by code analyzer 140 as a block of code that maypossibly modify the instance variable.

In additional, code analyzer 140 may also initially determine whetherthe assigned value is the default initial constant value for thevariable's type (as part of the variable's declaration). Thus, in someembodiments, if an instance variable is initialized to a value that isnot its default initial constant value, code analyzer 140 may, withoutperforming any additional code analysis regarding that instance variabledeclaration, determine that the assignment is definitely not redundantand may continue to analyze other instance variable declarations.

While described herein mainly in terms of Java-based examples, RedundantInstance Variable Initialization Elision may be utilized with any ofvarious programming languages according to different embodiments. Forinstance, when implementing Redundant Instance Variable InitializationElision, code analyzer 140 may have to analyze source code 120 toidentify various situations in which an instance variable may bemodified according to the specific nature of the particular programminglanguage.

In general, code analyzer 140 may be configured to determine whether thesource code 120 includes any earlier blocks of code, executable prior tothe instance variable declaration assignment (according to an executionorder for the source code) that comprise any of: a method invocation, aclass construction involving the instance variable (e.g., such as aninner class construction), a class construction involving an object thatincludes the instance variable (e.g., such as an new class constructionbeing passed ‘this’), an expression or other instruction involving anobject that includes the instance variable (e.g., an expression orinstruction that includes ‘this’), or that may otherwise access theinstance variable directly or via an indirect reference (e.g., aliasing‘this’), according to various embodiments.

If, as indicated by the negative output of decision block 510, noearlier code block includes a method invocation, an inner classconstruction, a lambda expression capturing ‘this’, a new classconstruction that is passed ‘this’, or an assignment with ‘this’ on theright side, the code analyzer 140 may determine that the instancevariable declaration assignment is definitely redundant, as in block530.

Alternatively, if the code analyzer 140 determines that any earlier codeblocks do include a method invocation, an inner class construction, alambda expression capturing ‘this’, a new class construction that ispassed ‘this’, or an assignment with ‘this’ on the right side, asindicated by the positive output of decision block 510, the codeanalyzer 140 may apply the set of rules recursively to each earlier codeblock that includes a method invocation, an inner class construction, alambda expression capturing ‘this’, a new class construction that ispassed ‘this’, or an assignment with ‘this’ on the right side, as shownin block 520.

When recursively applying the set of rules (e.g., analysis rules 150),code analyzer 140 may follow a chain of locations (e.g., within thecode) that can potentially (or possibly) change the value of theinstance variable. In some embodiments, code analyzer 140 may follow thepath from where the variable is initialized to the potential locations(e.g., within the code) where the variable can be mutated and analyzethose locations. For example, when determining whether to analyze thebody of method, code analyzer 140 may take into account the type ofmethod that is used. For instance, according to a Java-based embodiment,a method call may be private, final, and/or static. Similarly, codeanalyzer 140 may analyze constructor calls and Lambda instructions.

And we have discussed before, if a method is public, code analyzer 140may not be able to determine which method body may be executed atruntime due to overriding. Thus, code analyzer 140 may not be able todetermine whether an instance variable assignment is redundant or notwhen a public method is involved (e.g., when a public method is calledprior to the instance method is declared).

Therefore, if a method is private and/or final, code analyzer 140 maythen examine the body of the method that will be executed and runtime,apply the analysis rules 150 to that method body and determine whetherthe method body includes any instructions that modify the particularinstance variable. Additionally, code analyzer 140 may determine whetherthe method body includes a method invocation, an inner classconstruction, a lambda expression capturing ‘this’, a new classconstruction that is passed ‘this’, or an assignment with ‘this’ on theright side, and if so, apply the analysis rules 150 recursively to thosesituations as well, according to some embodiments.

Similarly, if a method is static, behavior of a static method call maynot ever be dependent on runtime, according to a java-based example.Therefore, if a method is static, code analyzer 140 may then examine thebody of the method that will be executed and runtime, apply the analysisrules 150 to that method body and determine whether the method bodyincludes any instructions that modify the particular instance variable.As with private and/or final methods, code analyzer 140 may alsodetermine whether the body of a static method includes a methodinvocation, an inner class construction, a lambda expression capturing‘this’, a new class construction that is passed ‘this’, or an assignmentwith ‘this’ on the right side, and if so, apply the analysis rules 150recursively to those locations, according to some embodiments.

Similarly, when code analyzer 140 encounters inner class constructions,lambda expressions, new class constructions, or other instructions(e.g., assignments) that involve ‘this’, code analyzer 140 may attemptto examine those instructions, expressions and/or classes to determineand recursively apply the analysis rules 150, according to someembodiments. For example, in a Java-based embodiment, if code analyzer140 identifies an assignment where the right side includes the ‘this’token, code analyzer 140 may store the variable name on the left sideand continue analyzing replacing the ‘this’ token with the variablename.

Thus, code analyzer 140 may identify bodies of code proceeding (e.g., inexecution order) the instance variable declaration that couldpotentially (or possibly) assign a value to the variable, and mayanalyze each of the bodies to determine if the instance variable is‘definitely unassigned’. For instance, in a Java-based embodiment, codeanalyzer 140 may be configured to use the analysis of DefiniteAssignment of variables provided in the Java Language Specification,recursively.

Code analyzer 140 may then analyze each of the identified code bodies todetermine if the instance variable is ‘definitely unassigned’, asdescribed above. During analysis of the identified bodies, code analyzer140 may encounter other code bodies that could possibly assign a valueto the variable and if so, may identify those code bodies to berecursively analyzed. For example, in a Java-based embodiment, codeanalyzer 140 may be configured to determine whether a code body includesa method invocation, an inner class construction, a lambda expressioncapturing ‘this’, a new class construction that is passed ‘this’, or anassignment with ‘this’ on the right side.

Code analyzer 140 may continue to identify and analyze bodies of codethat could possibly modify the instance variable recursively until nomore bodies are identified that can be analyzed are found. If codeanalyzer 140 encounters a dynamic method invocation (e.g., an instancemethod invocation that is not one of a private and/or final method) isfound during the analysis, code analyzer 140 may stop its analysis ofthe particular instance variable, and may determine that it may not bepossible to definitely determine whether the instance variable'sinitialization assignment is redundant or not, according to someembodiments.

If, after examining and analyzing all the possible locationsrecursively, code analyzer 140 does not encounter a reference to theinstance variable and also does not encounter a situation that preventsanalysis (e.g., a public or overridable method), code analyzer 140 maythen determine that the instance variable assignment is definitelyredundant.

Thus, as noted previously, Redundant Instance Variable InitializationElision, as described herein, may, according to various embodiments,identify three different categories of instance variable initializationassignment: 1) definitely redundant and it can be safely omitted from acompiled version of the code, 2) definitely not redundant because thecode analyzer encounters a modification to the instance variable and nowarnings may be generated, 3) possibly redundant where it is notpossible to determine statically that there is no modification to theinstance variable, but in which there may not actually be a modificationto the instance variable at runtime.

FIG. 6 is a flowchart illustrating one embodiment of a method forRedundant Instance Variable Initialization Elision, as described herein.The flowchart illustrated in FIG. illustrates, at a high level, theoverall outcome of applying Redundant Instance Variable InitializationElision according to some embodiments. Thus, as described above, a codeanalyzer 140 may analyze instance variable declaration with anassignment to determine whether that assignment is redundant or not, asshown in block 600.

If code analyzer 140 is able to determine that the instance variabledeclaration assignment is definitely not redundant, as indicated by thepositive output of decision block 610, code analyzer may not generateany warnings, hints, etc. For instance, the assignment may assign avalue to the variable that is not equal to the variable's defaultinitial constant value or code analyzer may have been able to positivelydetermine that the instance variable was modified prior to itsdeclaration. Thus, the positive output of decision block 610 may beconsidered to correspond to the second category of assignments describedabove.

If code analyzer 140 is not able to determine that the assignment isdefinitely not redundant, code analyzer 140 may then determine whetherthe instance variable declaration assignment is definitely redundant, asshown in decision block 620. For instance, code analyzer 140 may analyzeone or more bodies of code that may possibly modify the instancevariable and recursively apply analysis rules 150 to each body, asdescribed above. If, as indicated by the positive output of decisionblock 630, code analyzer 140 determines that the instance variabledeclaration assignment is definitely redundant, code analyzer 140 maythen cause the assignment to be omitted from the compiled code, as inblock 630. For instance, code analyzer 140 may communicate with compiler160, such as via one or more compiler hints, redundancy reports, etc.,such that compiler 160 may omit that particular assignment from compiledcode 180 when compiling source code 120. Thus, the positive output ofdecision block 620 may be considered to correspond to the first categoryof assignments described above.

However, if code analyzer 140 determines that the instance variabledeclaration assignment is neither definitely redundant nor definitelynot redundant, as indicated by the negative output of decision block620, code analyzer 140 may indicate, issue a warning, or otherwisecommunicate that the assignment is possibly redundant, as shown in block640. For instance, while applying analysis rules 150, code analyzer 140may have encountered an overridable method invocation and thus wasunable to determine with certainty whether a particular instancevariable assignment was definitely redundant or definitely notredundant. Thus, the negative output of decision block 640 may beconsidered to correspond to the third category of assignments describedabove.

In at least some embodiments, a computer system that implements aportion or all of one or more of the technologies described herein mayinclude a general-purpose computer system that includes or is configuredto access one or more computer-readable media. FIG. 7 illustrates such ageneral-purpose computing device 3000 suitable for implementing themethod, features and enhancements described herein. In the illustratedembodiment, computing device 3000 includes one or more processors 3010coupled to a system memory 3020 via an input/output (I/O) interface3030. Computing device 3000 further includes a network interface 3040coupled to I/O interface 3030.

In various embodiments, computing device 3000 may be a uniprocessorsystem including one processor 3010 or a multiprocessor system includingseveral processors 3010 (e.g., two, four, eight, or another suitablenumber). Processors 3010 may include any suitable processors capable ofexecuting instructions. For example, in various embodiments, processors3010 may be general-purpose or embedded processors implementing any of avariety of instruction set architectures (ISAs), such as the x86,PowerPC, SPARC, or MIPS ISAs, or any other suitable ISA. Inmultiprocessor systems, each of processors 3010 may commonly, but notnecessarily, implement the same ISA.

System memory 3020 may be configured to store program instructions anddata accessible by processor(s) 3010. In various embodiments, systemmemory 3020 may be implemented using any suitable memory technology,such as static random access memory (SRAM), synchronous dynamic RAM(SDRAM), nonvolatile/Flash-type memory, or any other type of memory. Inthe illustrated embodiment, program instructions and data implementingone or more desired functions, such as those methods, techniques, anddata described above, are shown stored within system memory 3020 as code(i.e., program instructions) 3025 and data 3026. For example, memory3020 and well as code 3025 and data 3026 may store, in one embodiment,program instructions and data for implementing integrated developmentenvironment 100, code analyzer 140 and/or compiler 160, described above.

In various embodiments, integrated development environment 100, codeanalyzer 140 and/or compiler 160 (and/or any individual sub-modulesthereof) may each be implemented in any of various programming languagesor methods. For example, in one embodiment, integrated developmentenvironment 100, code analyzer 140 and/or compiler 160 may be written inany of the Java, C, C++, assembly, or other general purpose programminglanguages, while in another embodiment, one or more of them may bewritten using a different, more specialized, programming language.Moreover, in some embodiments, integrated development environment 100,code analyzer 140 and/or compiler 160 (and/or various sub-modulesthereof) may not be implemented using the same programming language.

In one embodiment, I/O interface 3030 may be configured to coordinateI/O traffic between processor 3010, system memory 3020, and anyperipheral devices in the device, including network interface 3040 orother peripheral interfaces. In some embodiments, I/O interface 3030 mayperform any necessary protocol, timing or other data transformations toconvert data signals from one component (e.g., system memory 3020) intoa format suitable for use by another component (e.g., processor 3010).In some embodiments, I/O interface 3030 may include support for devicesattached through various types of peripheral buses, such as a variant ofthe Peripheral Component Interconnect (PCI) bus standard or theUniversal Serial Bus (USB) standard, for example. Also, in someembodiments some or all of the functionality of I/O interface 3030, suchas an interface to system memory 3020, may be incorporated directly intoprocessor 3010.

Network interface 3040 may be configured to allow data to be exchangedbetween computing device 3000 and other devices 3060 attached to anetwork or networks 3050. In various embodiments, network interface 3040may support communication via any suitable wired or wireless generaldata networks, such as types of Ethernet network, for example.

In some embodiments, system memory 3020 may be one embodiment of acomputer-readable (e.g., computer-accessible) medium configured to storeprogram instructions and data as described above with respect to FIGS.1-6 for implementing embodiments of the corresponding methods andapparatus. However, in other embodiments, program instructions and/ordata may be received, sent or stored upon different types ofcomputer-readable media. Generally speaking, a computer-readable mediummay include non-transitory storage media or memory media such asmagnetic or optical media, e.g., disk or DVD/CD coupled to computingdevice 3000 via I/O interface 3030. A non-transitory computer-readablestorage medium may also include any volatile or non-volatile media suchas RAM (e.g. SDRAM, DDR SDRAM, RDRAM, SRAM, etc.), ROM, etc., that maybe included in some embodiments of computing device 3000 as systemmemory 3020 or another type of memory.

Further, a computer-readable medium may include transmission media orsignals such as electrical, electromagnetic, or digital signals,conveyed via a communication medium such as a network and/or a wirelesslink, such as may be implemented via network interface 3040. Portions orall of multiple computing devices such as that illustrated in FIG. 7 maybe used to implement the described functionality in various embodiments;for example, software components running on a variety of differentdevices and servers may collaborate to provide the functionality. Insome embodiments, portions of the described functionality may beimplemented using storage devices, network devices, or special-purposecomputer systems, in addition to or instead of being implemented usinggeneral-purpose computer systems. The term “computing device,” as usedherein, refers to at least all these types of devices, and is notlimited to these types of devices.

Various embodiments may further include receiving, sending, or storinginstructions and/or data implemented in accordance with the foregoingdescription upon a computer-readable medium or upon a computer-readablestorage medium. Generally speaking, a computer-readable medium mayinclude storage media or memory media such as magnetic or optical media,e.g., disk or DVD/CD-ROM, volatile or non-volatile media such as RAM(e.g. SDRAM, DDR, RDRAM, SRAM, etc.), ROM, etc. In some embodiments, acomputer-readable medium may also include transmission media or signalssuch as electrical, electromagnetic, or digital signals, conveyed via acommunication medium such as network and/or a wireless link.

The various methods as illustrated in the figures and described hereinrepresent exemplary embodiments of methods. The methods may beimplemented in software, hardware, or a combination thereof. In variousof the methods, the order of the steps may be changed, and variouselements may be added, reordered, combined, omitted, modified, etc.Various of the steps may be performed automatically (e.g., without beingdirectly prompted by user input) and/or programmatically (e.g.,according to program instructions).

While various systems and methods have been described herein withreference to, and in the context of, specific embodiments, it will beunderstood that these embodiments are illustrative and that the scope ofthe disclosure is not limited to these specific embodiments. Manyvariations, modifications, additions, and improvements are possible. Forexample, the blocks and logic units identified in the description arefor understanding the described embodiments and not meant to limit thedisclosure. For example, actions, processes, methods, tasks or functionsdescribed herein as being performed by code analyzer 140 may, in someembodiments, be performed by compiler 160 and vice versa. Additionally,functionality may be separated or combined in blocks differently invarious realizations of the systems and methods described herein ordescribed with different terminology.

These embodiments are meant to be illustrative and not limiting.Accordingly, plural instances may be provided for components describedherein as a single instance. Boundaries between various components,operations and data stores are somewhat arbitrary, and particularoperations are illustrated in the context of specific illustrativeconfigurations. Other allocations of functionality are envisioned andmay fall within the scope of examples that follow. Finally, structuresand functionality presented as discrete components in the exemplaryconfigurations may be implemented as a combined structure or component.

The various methods as illustrated in the figures and described hereinrepresent example embodiments of methods. The methods may be implementedin software, hardware, or a combination thereof. The order of method maybe changed, and various elements may be added, reordered, combined,omitted, modified, etc.

Although the embodiments above have been described in detail, numerousvariations and modifications will become apparent once the abovedisclosure is fully appreciated. Various modifications and changes maybe made as would be obvious to a person skilled in the art having thebenefit of this disclosure. It is intended that the invention embraceall such modifications and changes and, accordingly, the abovedescription to be regarded in an illustrative rather than a restrictivesense. Furthermore, it is intended that the following claims beinterpreted to embrace all such variations and modifications.

What is claimed is:
 1. A non-transitory, computer-readable storagemedium storing program instructions that when executed on a computingdevice cause the computing device to perform: implementing a codeanalyzer configured to: access source code; identify, within the sourcecode, an instance variable declaration comprising an assignment thatassigns a value to an instance variable; determine whether the assignedvalue is a default value for the instance variable; apply, based atleast in part on determining that the assigned value is a default valuefor the instance variable, a set of rules to determine whether theinstance variable declaration assignment is definitely redundant withrespect to the default value; and indicate, based at least in part ondetermining that the instance variable declaration assignment isdefinitely redundant, that the instance variable declaration assignmentis definitely redundant.
 2. The non-transitory, computer-readablestorage medium of claim 1, wherein the code analyzer is furtherconfigured to: determine that the assigned value is not the defaultvalue for the instance variable; and in response to determining that theassigned value is not the default value, determine that the instancevariable declaration assignment is definitely not redundant with respectto the default value such that no indication is made regarding theinstance variable declaration assignment being definitely redundant. 3.The non-transitory, computer-readable storage medium of claim 1, whereinto apply the set of rules, the code analyzer is configured to: determinewhether the instance variable is assigned a value prior to the instancevariable declaration assignment according to an execution order of thesource code.
 4. The non-transitory, computer-readable storage medium ofclaim 3, wherein the code analyzer is further configured to: determine,based at least in part on determining that the instance variable isassigned a value prior to the instance variable declaration assignment,that the instance variable declaration is definitely not redundant withrespect to the default value.
 5. The non-transitory, computer-readablestorage medium of claim 1, wherein to determine whether the instancevariable declaration assignment is definitely redundant, the codeanalyzer is further configured to: determine whether the source codeincludes one or more earlier blocks of code, executable prior to theinstance variable declaration assignment according to an execution orderof the source code, that assign a value to the instance variable; anddetermine, based at least in part on determining that the source codedoes not include one or more earlier blocks of code that assign a valueto the instance variable, that the instance variable declarationassignment is definitely redundant with respect to the default value. 6.The non-transitory, computer-readable storage medium of claim 1, whereinto determine whether the instance variable declaration assignment isdefinitely redundant, the code analyzer is further configured to:determine whether the source code includes one or more earlier blocks ofcode, executable prior to the instance variable declaration assignmentaccording to an execution order of the source code, that possibly assigna value to the instance variable; and apply, based at least in part ondetermining that the source code includes one or more earlier blocks ofcode that possibly assigns a value to the instance variable, the set ofrules to each of the one or more earlier blocks of code to determinewhether the one or more earlier blocks of code assign a value to theinstance variable.
 7. The non-transitory, computer-readable storagemedium of claim 6, wherein the code analyzer is further configured to:determine, based at least in part on applying the set of rules to eachof the one or more earlier blocks of code, that none of the one or moreearlier blocks of code assign a value to the instance variable; anddetermine, based at least in part on determining that none of the one ormore earlier blocks of code assign a value to the instance variable,that the instance variable declaration is definitely redundant withrespect to the default value.
 8. The non-transitory, computer-readablestorage medium of claim 6, wherein the code analyzer is furtherconfigured to: determine, based at least in part on applying the set ofrules to each of the one or more earlier blocks of code, that at leastone of the one or more earlier blocks of code assigns a value to theinstance variable; and determine, based at least in part on determiningthat the at least of the one or more earlier blocks of code assigns avalue to the instance variable, that the instance variable declarationis definitely not redundant with respect to the default value.
 9. Thenon-transitory, computer-readable storage medium of claim 6, wherein todetermine whether the source code includes one or more earlier blocks ofcode that possibly assign a value to the instance variable, the codeanalyzer is further configured to: determine whether the source codeincludes any earlier blocks of code, executable prior to the instancevariable declaration assignment according to an execution order for thesource code, that comprise any of: a method invocation; a classconstruction involving the instance variable; a class constructioninvolving an object that includes the instance variable; an expressioninvolving the object that includes the instance variable; or aninstruction involving the object that includes the instance variable.10. The non-transitory, computer-readable storage medium of claim 1,wherein the code analyzer is further configured to: determine that thesource code includes one or more earlier blocks of code, executableprior to the instance variable declaration assignment according to anexecution order of the source code, that possibly assign a value to theinstance variable; apply the set of rules to each of the one or moreearlier blocks of code; determine, based at least in part on applyingthe set of rules to each of the one or more earlier blocks of code, thatit cannot be determined, for at least one of the one or more earlierblocks of code, whether the at least one earlier block of code assigns avalue to the instance variable declaration assignment; and indicate thatit cannot be determined whether the instance variable declarationassignment is definitely redundant with respect to the default value.11. The non-transitory, computer-readable storage medium of claim 1,wherein the code analyzer is further configured to: include a compilerhint in the source code indicating that the instance variabledeclaration assignment should not be included in a compiled version ofthe source code.
 12. A computing device, comprising: a processor; and amemory comprising program instructions, that when executed on theprocessor cause the processor to implement a code analyzer configuredto: access source code; identify, within the source code, an instancevariable declaration comprising an assignment that assigns a value to aninstance variable; determine whether the assigned value is a defaultvalue for the instance variable; apply, based at least in part ondetermining that the assigned value is a default value for the instancevariable, a set of rules to determine whether the instance variabledeclaration assignment is definitely redundant with respect to thedefault value; and indicate, based at least in part on determining thatthe instance variable declaration assignment is definitely redundant,that the instance variable declaration assignment is definitelyredundant.
 13. The computing device of claim 12, wherein to determinewhether the instance variable declaration assignment is definitelyredundant, the code analyzer is further configured to: determine thatthe instance variable is assigned a value prior to the instance variabledeclaration according to an execution order of the source code; and inresponse to determining that the instance variable is assigned a valueprior to the instance variable declaration, determine that the instancevariable is definitely not redundant with respect to the default valuesuch that no indication is made regarding the instance variabledeclaration assignment being definitely redundant.
 14. The computingdevice of claim 12, wherein to determine whether the instance variabledeclaration assignment is definitely redundant, the code analyzer isfurther configured to: determine whether the source code includes one ormore earlier blocks of code, executable prior to the instance variabledeclaration assignment according to an execution order of the sourcecode, that assign a value to the instance variable; and determine, basedat least in part on determining that the source code does not includeone or more earlier blocks of code that assign a value to the instancevariable, that the instance variable declaration assignment isdefinitely redundant with respect to the default value.
 15. Thecomputing device of claim 12, wherein to determine whether the instancevariable declaration assignment is definitely redundant, the codeanalyzer is further configured to: determine whether the source codeincludes one or more earlier blocks of code, executable prior to theinstance variable declaration assignment according to an execution orderof the source code, that possibly assign a value to the instancevariable; and apply, based at least in part on determining that thesource code includes one or more earlier blocks of code that possiblyassign a value to the instance variable, the set of rules to each of theone or more earlier blocks of code to determine whether the one or moreearlier blocks of code assign a value to the instance variable.
 16. Thecomputing device of claim 15, wherein the code analyzer is furtherconfigured to: determine, based at least in part on applying the set ofrules to each of the one or more earlier blocks of code, that none ofthe one or more earlier blocks of code assign a value to the instancevariable; and determine, based at least in part on determining that noneof the one or more earlier blocks of code assign a value to the instancevariable, that the instance variable declaration is definitely redundantwith respect to the default value.
 17. The computing device of claim 15,wherein the code analyzer is further configured to: determine, based atleast in part on applying the set of rules to each of the one or moreearlier blocks of code, that at least one of the one or more earlierblocks of code assigns a value to the instance variable; and determine,based at least in part on determining that the at least of the one ormore earlier blocks of code assigns a value to the instance variable,that the instance variable declaration is definitely not redundant withrespect to the default value.
 18. The computing device of claim 12,wherein to determine whether the source code includes one or moreearlier blocks of code that possibly assign a value to the instancevariable, the code analyzer is further configured to: determine whetherthe source code includes any earlier blocks of code, executable prior tothe instance variable declaration assignment according to an executionorder for the source code, that comprise any of: a private or finalinstance method invocation on an object pointer to an object thatincludes the instance variable; a stable method invocation that receivesan object pointer to an object that includes the instance variable; aninner class construction involving the instance variable; a lambdaexpression that captures an object pointer to an object that includesthe instance variable; or a new class construction that receives anobject pointer to an object that includes the instance variable.
 19. Thecomputing device of claim 12, wherein the program instructions furthercause the computing device to: implement a compiler configured to:compile the source code to generate a compiled version of the sourcecode; and omit, in response to the indication that the instance variabledeclaration assignment should not be included in a compiled version ofthe source code, the instance variable declaration assignment from thecompiled version of the source code.
 20. A computer implemented method,comprising: accessing, by a code analyzer, source code; identifyingwithin the source code, by the code analyzer, an instance variabledeclaration comprising an assignment that assigns a value to an instancevariable; determining, by the code analyzer, whether the assigned valueis a default value for the instance variable; applying, by the codeanalyzer based at least in part on determining that the assigned valueis a default value for the instance variable, a set of rules todetermine whether the instance variable declaration assignment isdefinitely redundant with respect to the default value; and indicating,by the code analyzer based at least in part on determining that theinstance variable declaration assignment is definitely redundant, thatthe instance variable declaration is definitely redundant.